Documentation for “Zerocat Chipflasher: ‘kick’”
Generated on: Tue, 03 Dec 2024 13:38:54 +0100
Repository: git://zerocat.org/zerocat/projects/chipflasher
Board: board-v2.0.0-1244-4270742b1
Version: v2.0.2-0-4270742b1
Branch: flashrom-interface
kick
connect
.kick
, the First FirmwareTo configure kick
for board v2 (e.g. Chipflasher v2), the
default, type:
[env]$ make -C ../../firmware1/src config-BOARD_V2
To configure kick
for board v1 (e.g. Chipflasher “board-edition-1”),
type:
[env]$ make -C ../../firmware1/src config-BOARD_V1
The host utility and the firmware use a serial connection for their communication. The speed of that connection is specified as baudrate.
The default baudrate is: 115200
Baudrate configuration is retrieved from file ../../firmware1/start/board.cfg, which in turn is managed via ../../firmware1/start/Makefile.
To build kick
, type:
[env]$ make -C ../../firmware1/src kick
To get a full list of available targets, type:
[env]$ make -C ../../firmware1/src help
To clean files and folders, type:
[env]$ make -C ../../firmware1/src clean
kick
To upload kick
to onboard, free-design RAM, type:
[env]$ make -C ../../firmware1/start kick-ram
To upload kick
to onboard, proprietary-design EEPROM, type:
[env]$ make -C ../../firmware1/start kick-eeprom
To get a full list of available targets, type:
[env]$ make -C ../../firmware1/start help